Method of and system for providing namespace based object to XML mapping

ABSTRACT

The present invention relates generally to computers and computer databases, and more specifically, to a method of and system for converting between Object-oriented classes and markup languages. One aspect of the invention is broadly defined as a method for converting data from a markup language format to an Object model, comprising the steps of: identifying an input markup language code, a destination Object and a markup schema; determining mappings between the schema and the destination Object, including identification of namespaces associated with elements of the input markup language document; traversing the input markup language document; and instantiating corresponding software Objects with consideration for the namespace.

The present invention relates generally to computers and computer databases, and more specifically, to a method of and system for converting between Object-oriented classes and markup languages.

BACKGROUND OF THE INVENTION

Object-oriented software languages are an attempt to mirror the real world, in the sense that “physical” Objects are identified, and certain functionality is associated with each given Object. Software Objects are not easily portable, so it is common to convert software Objects to markup language code for transmission over the Internet, re-assembling the Objects when they are received. In fact, a number of protocols have been developed to support the communication of XML data over the Internet. It is therefore much easier to transmit database queries and structures, for example, over the Internet using XML (eXtensible Markup Language) code rather than Java Objects.

XML is a standard, software development language-independent text format for representing data. XML is a markup language in the same sense as Standard Generalized Markup Language (SGML), and Hyper Text Markup Language (HTML). This paradigm allows XML to facilitate communication between disparate systems—as long as all of the parties involved understand the particular XML model, the nature of the model itself is irrelevant and independent of the platforms involved.

This universal “understanding” of XML documents is facilitated by the use of XML schema. A set of syntax rules for XML elements shared by a group of XML documents is defined by an XML schema, which is an XML document itself. The syntax rules may, for example, indicate what elements can be used in a document, define the order in which they should appear, define which elements have attributes and what those attributes are, and identify any restrictions on the type of data or number of occurrences of an element. Schemas can be custom designed, though many schema are established by standards groups for general areas of application.

Two specific advantages of XML in the handling and transmission of Object-oriented software systems over Internet networks are:

-   -   1. Configuration: XML documents are a common way of storing         configuration information—for example, EJB (Enterprise Java         Beans) deployment descriptions and WSDL (Web Services         Description Language) files that describe web services, are both         in XML format. Object-XML conversion technologies allow a         developer to interact with the data as recognizable domain         Objects instead of having to use XML specific APIs and data         structures; and     -   2. Persistence: It is easier to store XML documents than         Objects. XML documents can either be stored directly to         something like a file, to an EIS (Enterprise Integration         Systems) data store that accepts XML records, or to an XML         database.

Converting back and forth between XML and software Objects is not a trivial task. While XML represents data as a plain text document composed of a series of elements in a hierarchical format, software Objects in an Object-oriented application are composed of a complex set of data-types, pointers, application rules/methods, inheritance and relationships to other Objects. It is not surprising that the attempts at tools which can convert between software Objects and XML, have not been particularly effective. Two such families of tools include “Direct Converters” and “Code Generators”:

Direct Converters

One family of Object-XML conversion tools are known as “direct converters”. This family includes, for example: “XStream”, the details of which may be found on the Internet at http://xstream.codehaus.org/ and “betwixt” which may be found at http://jakarta.apache.org/commons/betwixt/. These tools employ a fixed set of rules determining how an Object is converted to and from XML.

A first example of how an Object could be converted to an XML format using a direct converter is presented in FIG. 1. In this example the Class names and attribute names in the Java class become the element names in the resulting XML document (different direct converters may have different algorithms, but this is the general approach). The attribute firstName with value “Jane” in the Object 12, becomes a line of XML code in the XML document 14 reading “<firstName>Jane</firstName>”. Similarly, the secondName attribute with value “Doe” becomes a line of XML code reading “<secondName>Doe</secondName>”. The city and street data are similarly transposed from the Address Object to the XML document.

If the Object model is changed as shown in the second direct converter example, presented in FIG. 2, then a different XML document will be produced. In this case, the name of the “city” attribute of FIG. 1 has been changed to “town”. This “town” attribute will be converted to a line of XML code reading <town>Some Town</town> rather than <city>Some Town</city> as in FIG. 1.

Using direct conversion tools, the XML document will reflect the structure of whatever Java Objects happen to arrive. Thus, there is no guarantee that an arriving document will conform to a given XML Schema.

In the third example of direct converters, presented in FIG. 3, the “city” attribute in the “Address” class was renamed to “town”. If the XML document does not conform to the rules necessary to convert it to the Object then it cannot be converted using a direct conversion tool. A direct converter solution is only useful if you do not care how the XML data is formed—in this third example the “town” element cannot be converted to the “city” attribute in the “Address” class.

Generally, one does care how XML and Object data are transformed, so direct conversion techniques are of very limited usefulness.

Code Generators

A second family of Object-XML conversion tools is referred to as “code generated solutions”. Code generated solutions take an XML Schema or some other XML document structure definition such as a DTD (document type definition) and produce an Object model from that. The advantage of this approach over data converters is that the resulting document will conform to the XML Schema. Two examples of “code generators” are JAXB which is described on the Internet at http://Java.sun.com/xml/jaxb/index.jsp, and BEA XML Beans which is described at http://dev2dev.bea.com/technologies/xmlbeans/index.jsp.

For example, assume that the following XML schema is given to generate an Object model:

<?xml version=“1.0” encoding=“UTF-8”?> <xs:schema xmlns:xs=“http://www.w3.org/2001/XMLSchema”   elementFormDefault=“qualified” attributeFormDefault=   “unqualified”>   <xs:element name=“employee”>     <xs:complexType>       <xs:sequence>         <xs:element ref=“personal-info”/>       </xs:sequence>     </xs:complexType>   </xs:element>   <xs:element name=“personal-info”>     <xs:complexType>       <xs:sequence>         <xs:element name=“first-name” type=“xs:string”/>         <xs:element name=“last-name” type=“xs:string”/>       </xs:sequence>     </xs:complexType>   </xs:element> </xs:schema> Then something similar to the following will be generated by code generated solutions:

The key point is that a “PersonalInfo” class is generated by a code generated approach. This does not follow with object-oriented programming since an “Employee” object with attributes “firstName” and “lastName” is required to model the data. In fact, code generated solutions do not allow any control over the nature of the Objects which are generated. Hence, code generation tools are useful when you care about the XML schema but not about the Object model.

“Code generator” Object to XML conversion tools can only infer very limited meaning on the structures that they encounter in the XML document. For example, they typically generate a separate Object for each XML element, nesting these Objects within one another as required by the XML structure. As well, the existing tools do not appreciate that some XML elements contain data while others are used to organize data. This results in a complicated, cumbersome Object structure which does not reflect what is desired or what is intuitive to the user.

A more powerful family of XML to Object conversion tools have been evolving, referred to as “mapping” tools. These tools allow the user to manually define how the XML and Objects are to be converted back and forth. However, the existing mapping tools are deficient in a number of ways.

In particular, these mapping tools (along with the direct converters and code generators which preceded them) convert between XML and Objects in a way that does not give any regard to the use of namespaces in an XML document.

Namespaces are commonly used in XML to associate elements with their XML vocabularies. This provides great flexibility as it allows multiple vocabularies to be used in a single document without worrying about name conflicts and confusion. It also allows the user to audit the system, simplifying the process of identifying which party defined each term.

Because the known mapping tools, direct converters and code generators do not give any regard to namespaces in an XML document, their use is limited to XML documents in which namespaces are not used to distinguish between elements which have the same name. If the known methodologies are used with such XML documents, then the system generally provides errors or nonsensical information. Clearly, this is a critical shortcoming.

It is therefore desirable to provide a method and system for converting data between Object-oriented classes and markup languages which can properly handle XML documents which include elements of the same name, having different namespaces. This solution should be provided with consideration for the problems described above.

It is also desirable to provide a namespace-consistent system and method, which takes the paths and structures of the markup language and software Objects into consideration.

SUMMARY OF THE INVENTION

It is therefore an object of the invention to provide a method and system which obviates or mitigates at least one of the disadvantages described above.

One aspect of the invention is broadly defined as a method for converting data from a markup language format to an Object model, comprising the steps of: identifying an input markup language document, a destination Object model and a markup schema; determining mappings between the input markup schema and the destination Object model, including identification of namespaces associated with elements of the input markup language document; traversing the input markup language document; and instantiating the corresponding software Objects with consideration for the namespaces.

Another aspect of the invention is defined as a method for converting data in an Object model format to a markup language format, comprising the steps of: identifying an input Object, a destination markup language document, and a markup schema; determining mappings between the input Object and the markup schema, including identification of namespaces associated with elements of the input markup language document; considering each software Object, generating corresponding markup code and placing elements with the appropriate namespace; and storing the generated markup language code in the destination markup language document.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of the invention will become more apparent from the following description in which reference is made to the appended drawings in which:

FIG. 1 presents a block diagram of a first exemplary conversion between software Objects and an XML document using a direct converter, as known in the art;

FIG. 2 presents a block diagram of a second exemplary conversion between software Objects and an XML document using a direct converter, as known in the art;

FIG. 3 presents a block diagram of a third exemplary conversion between software Objects and an XML document using a direct converter, as known in the art;

FIG. 4 presents a flow chart of a method of conversion between a markup language document and an Object, in a broad embodiment of the invention;

FIG. 5 presents a flow chart of a method of conversion between an Object and a markup language document, in a broad embodiment of the invention;

FIG. 6 presents a block diagram of an exemplary computer system on which the methods of the invention could be implemented;

FIG. 7 presents a flow chart of a method of set-up for conversion of data between XML and Object formats, in an embodiment of the invention;

FIG. 8 presents a flow chart of a method of run-time for conversion of data from XML format to Object format, in an embodiment of the invention; and

FIG. 9 presents a flow chart of a method of run-time for conversion of data from Object format to XML format in an embodiment of the invention.

DESCRIPTION OF THE INVENTION

The broad concept of the invention takes namespace information into consideration so that the user is able to correctly convert between markup language formats and Object models. Other approaches to XML to Object conversion do not give any regard to namespaces and store elements with the same name, in a collection.

The invention also recognizes that some XML elements contain data and others are used solely to organize data. This allows the user to maintain a well-structured document without having to produce additional Objects. Other conversion tools cannot distinguish between data elements and organizational elements, and require that an Object be created for each level of nesting. For example, a code generator cannot infer which elements contain relevant content versus elements that are used solely to organize data, since that type of information is not stored in the XML schema. The invention provides the user with the ability to customize mappings taking XML position and structure into consideration. Attributes and elements in an XML document are not required to be uniquely identified by name, instead it is a combination of name and position that represent what a node means.

Methodologies which broadly address the objects outlined above, are presented as flow charts in FIGS. 4 and 5. FIG. 4 presents a flow chart of markup language to software Object conversion, while FIG. 5 presents a flow chart of complementary Object to markup language conversion. Markup language documents include elements that are defined by tags, labels or similar indicators. The method of the invention is generally described with respect to XML, but could apply to any mark up language including XML, Standard Generalized Markup Language (SGML), Hyper Text Markup Language (HTML), Extensible HTML (XHTML). The invention could also be applied to other mark up languages which may evolve over time.

Similarly, the invention is generally described with respect to Java, but could apply to any Object-oriented language. Common Object-oriented software languages include C++, Eiffel™, Smalltalk™ and Java™. Of these, Java is the most widely used, particularly in Internet-based applications.

XML documents have both a logical and a physical structure. Logically, the XML document is composed of declarations, elements, comments, character references, and processing instructions. The elements can contain text and other elements. Attributes in XML provide additional information regarding an element.

An Object model, such as Java, contains one or more Object classes. An Object class contains attributes, relationships and/or methods. The attributes store primitive data such as integers, and also store simple types, such as String and Date. Relationships are references to other classes, while methods are paths of query execution.

The process of converting a markup language document to Object format is presented in the flow chart of FIG. 4. To begin with, the targeted files and mark up schema must be identified at step 40. This could occur in a number of ways, depending on the application. For example, a response to a database query could arrive at a client computer in a markup language format. This query would also generally include a schema with it or make reference to a known schema.

At step 42, mappings between the received markup language document and the desired Object are determined, generally by correlating the schema to the Object(s). This step could also be performed in a number of ways, for example, using a graphic user interface such as the Oracle TopLink Mapping Workbench (additional details are available in the related co-pending patent applications titled “Method and System for Mapping Between Markup Language Documents and an Object Model”, filed on Aug. 1, 2001, under U.S. patent application Ser. No. 09/920,786, “Method of and System for Providing Position Based Object to XML Mapping”, filed on Jun. 8, 2004, under U.S. patent application Ser. No. 10/864,850, and “Method of and System for Providing Path Based Object to XML Mapping”, filed on Jun. 8, 2004, under U.S. patent application Ser. No. 10/864,790, all of which are incorporated herein by reference). Alternatively, mappings could be established manually or in advance by a third party such as a standards group or a software supplier.

If, for example, an XML document with the following structure is being considered:

<CUSTOMER xmlns:first=“http://www.oracle.com/first”   xmlns:last=“http://www.oracle.com/last”>   <first:NAME>Jane</first:NAME>   <last:NAME>Doe</last:NAME> </CUSTOMER> then the user will probably wish to keep the first:NAME and second:NAME separate, mapping them onto corresponding “firstName” and “secondName” attributes of a Object representing a Customer. Prior art techniques will not allow this, because they do not consider the namespace identifiers in the XML code. That is, the prior art techniques essentially see two lines of XML code that have the same name: <NAME>Jane</NAME> and <NAME>Doe</NAME>; if these two lines of XML code were converted back to Java format, they would not look the same as the above. Thus, information would have been lost by the process.

In many applications of the invention, either standard schemas will be used or a vast number of markup documents will be handled, all of which use the same schema. In either case, it would be efficient to generate a mapping paradigm and store that paradigm for regular and multiple uses. The mapping paradigm could be transmitted to other users or even stored on CD-ROMs and distributed as part of a software application.

At step 44, the method of the invention simply traverses the markup language document, collecting data and text for the generation of software Objects at step 46. Step 44 could be performed in its entirety before step 46 is performed, or the two steps could be performed repeatedly for each of the elements of the markup language document. Alternatively, logical portions of the markup language document could be processed one block at a time. The manner in which these steps are performed is not significant in the context of the broad invention. What is important though, is that the process of traversing the markup language document at step 44 take into consideration the namespace data for a given markup language element.

Once all of the software Objects have been generated, the Object can be processed in whatever manner the software application dictates. In the case of a database system, for example, this may consist of simply executing the received query (in the case of a server receiving the packet), or reading the received response (in the case of a client computer).

Note that if multiple conversions are being made, it may only be necessary to perform steps 40 and 42 once, as part of a set-up routine. Steps 44 and 46 can then be performed multiple times thereafter, as part of a runtime routine.

The complementary process of converting software Objects to a mark up language format is presented in the flow chart of FIG. 5.

Like the method of FIG. 4, the process begins with the identification of the targeted documents and markup language schema at step 50. In this case, however, the main input being received will be an Object, rather than a markup language document. While a markup language document is not received in this algorithm, a schema must still be provided.

In the typical application of software Objects being used on computers and servers, with corresponding markup language documents being generated for transmission, this routine would be launched in response to a desire to transmit a query or a response. Hence, all of the information required to perform this routine would typically be local to the computer or server generating the markup language document.

Control then passes to step 52, where mappings between the software Object and the schema of the desired output markup language document are determined. This step would be performed in much the same manner as step 42 above, i.e. using a graphic user interface (GUI), via manual manipulation or being pre-determined. The only substantial difference is the nature of the data available to the user while they are establishing the mappings. In the case of Object to markup language conversion, for example, the user would have complete access to all of the details of the software Objects, but would not have access to the elements and structure of the markup language document that is to be generated. The user would be limited to structure and details provided by the schema and Object.

Much like step 42 above, the mapping data generated at step 52 correlates Objects with markup language elements, and with consideration for the namespaces of those elements. In the case of Object to markup language conversion, this is largely driven by the schema (for example, the schema may dictate that the first instance of “name” is the given name, and the second instance of “name” is the family name).

At step 54, the algorithm simply considers each of the software Objects, one at a time, generating corresponding markup language code. This would be done generally in the manner known in the art except that the mapping data is used to determine the namespace for each element in the generated markup language code of the markup language document. The manner is which this is done will be clear from the examples which are described hereinafter.

The generated markup language document is then stored at step 56 so it can be processed or transmitted as required. As in the case of the method of FIG. 4, steps 54 and 56 can be done one Object at a time, block by block, or completed in their entirety before continuing with the next step. As well, steps 50 and 52 could be performed a single time, while steps 54 and 56 are performed multiple times (for multiple Objects). The manner in which these steps are performed is not significant in the context of the broad invention.

An example of a system upon which the invention may be performed is presented as a block diagram in FIG. 6. This computer system 60 includes a display 62, keyboard 64, computer 66 and external devices 68.

The computer 66 may contain one or more processors or microprocessors, such as a central processing unit (CPU) 70. The CPU 70 performs arithmetic calculations and control functions to execute software stored in an internal memory 72, preferably random access memory (RAM) and/or read only memory (ROM), and possibly additional memory 74. The additional memory 74 may include, for example, mass memory storage, hard disk drives, floppy disk drives, magnetic tape drives, compact disk drives, program cartridges and cartridge interfaces such as that found in video game devices, removable memory chips such as EPROM, or PROM, or similar storage media as known in the art. This additional memory 74 may be physically internal to the computer 66, or external as shown in FIG. 6.

The computer system 60 may also include other means for allowing computer programs or other instructions to be loaded. Such means can include, for example, a communications interface 76 which allows software and data to be transferred between the computer system 60 and external systems. Examples of communications interface 76 can include a modem, a network interface such as an Ethernet card, a serial or parallel communications port. Software and data transferred via communications interface 76 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communications interface 76.

Input and output to and from the computer 66 is administered by the input/output (I/O) interface 78. This I/O interface 78 administers control of the display 62, keyboard 64, external devices 68 and other such components of the computer system 60.

The invention is described in these terms for convenience purposes only. It would be clear to one skilled in the art that the invention may be applied to other computer or control systems 60. Such systems would include all manner of appliances having computer or processor control including telephones, cellular telephones, televisions, television set top units, lap top computers, personal digital assistants and automobile telematic systems.

The solution of the invention recognizes that Attributes and Elements in an XML document are not required to be uniquely identified by name, instead it is a combination of name and namespace that represent what a node means. The namespace of an XML node is significant and the user should be able to use it to uniquely map the XML node to an attribute in their object model. Other approaches ignore namespace and store converted XML nodes to objects based on the local name.

The majority of Object-to-XML technologies are based on generating Java code from XML schemas. A code generator cannot infer any significance based on the namespace of an XML node, since that type of information is not stored in the schema. Since the invention provides the user the ability to customize the mappings it can provide capabilities beyond those of a typical code generation tool.

Further advantages are clear from the detailed description of the invention which follows.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS OF THE INVENTION

The preferred embodiment of the invention is presented by means of the flow charts of FIGS. 7, 8 and 9, and the descriptions of the examples which follow.

In general, the XML to Object conversion methodology of the invention is effected in two stages: the set-up stage and the run-time stage. The routine for the set-up stage is presented in the flow chart of FIG. 7. The set-up stage is common to both XML-to-Java conversion, and Java-to-XML conversion, though the data available to the user is usually different.

To begin with, the XML documents being dealt with must be identified. Specifically, the target XML document is identified at step 90, the XML schema being used is identified at step 92 and the target Java Object identified at step 94.

The system is then presented to the user via a graphical user interface (GUI) at step 96, which presents the XML elements defined by the schema and the destination Objects defined by Java class files. The GUI also allows the user to define how the two systems correlate. Suitable tools are known in the art for establishing such mappings, such as the Oracle TopLink Mapping Workbench. The necessary modifications to such a tool (or a similar tool) required to effect the invention would be clear to one skilled in the art from the teachings herein. Other mapping tools, of course, could also be used.

Particular to the invention is the functionality to map namespace information from an XML document to an Object. This is accomplished by:

-   1. presenting the namespace context of the XML elements in the XML     document to the user via the GUI, -   2. allowing elements in different namespaces to be identified and     correlated to Objects independently of one another, and -   3. including a field in the mapping data (i.e. the metadata for the     node), which includes namespace data.

The user is then able to establish correlations and relationships at step 98 which are analyzed and stored as a system of mappings at step 100. These mappings are referred to herein as the “metadata” for a given node. As part of this analysis, the algorithm records the Java Object attribute, and the path through the XML structure, including a textual identifier representing the namespace of the XML element in the XML document (the most logical namespace identifier, of course, is the use of the namespace text itself). Further details are described hereinafter, particularly with respect to Examples 1 and 4.

It is also desirable to allow the user to identify lines of XML code as either “simple” or “object” data, as this provides the user with much greater control over the structure of the system. Other Object-to-XML technologies require an Object relationship for each level of nesting. Hence, they generate an excessive number of levels and unnecessary complexity. In contrast, the invention recognizes that it is not necessary (or even desirable) to generate a separate level of Objects for each XML level—the invention allows one to define mappings which convert XML structure and data into fewer levels of Java Objects.

The solution of the invention recognizes that some elements in a markup language document contain data and others are used solely to organize data. This allows the user to maintain a well-structured document without having to produce additional software Objects. Other solutions cannot distinguish between data elements and organizational elements and require that an Object be created for each level of nesting.

The majority of Object-to-XML technologies are based on generating Java code from XML schemas. A code generator cannot infer which elements contain relevant content versus elements that are used solely to organize data, since that type of information is not stored in the schema. Since the invention provides the user with the ability to customize mappings, it can provide capabilities beyond what a code generation tool is capable of. Any application developer using an Object oriented computer language to interact with XML would likely be very interested in the capabilities of this invention.

This is done simply by allowing the user to identify whether an element is a simple element or an object element at the mapping stage, and then tagging the metadata accordingly. For example, the metadata for a simple element might read as follows. Note that the “mapping type” identifies whether the node is a simple element or an object element, and the “namespace resolver” includes the namespace itself (which maps prefixes from the XPath statement to the namespace URIs that they represent):

-   -   lastName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: lastName     -   XPath: last:NAME/text( )     -   Namespace resolver: last=“http://www.oracle.com/last”         The specified “XPath last:NAME/text( )” contains the section         “last:NAME” that the namespace resolver will use to convert that         string to the value pair (name=NAME,         namespace=http://www.oracle.com/last). When the XPath is         executed it will then look for the child node with name=“NAME”         and namespace=“http://www.oracle.com/last”.

Similarly, the metadata for an object element might read:

-   -   billingAddress Mapping     -   Mapping Type: composite Object mapping     -   Object Attribute: billingaddress     -   XPath: email:ADDRESS     -   Namespace resolver: email=“http://www.oracle.com/email”

This completes the “set-up” phase of the process. Note that set-up could be effected at any time prior to a run-time stage.

The methodology of the run-time stage for converting an XML document to a Java class representation is presented in the flow diagram of FIG. 8.

This methodology is generally initiated when an XML document or markup data of some sort is received by the program at step 110, and it is determined that this file must be converted from XML format to a Java representation. Of course, it is not necessary that an entire XML document be received—a short piece of XML code or a portion of a larger document is sufficient.

Conversion of an XML document generally consists of stepping through the XML document, considering each line, and determining via the mapping data, how it is to be realized in the Java code. Before starting this process, the program first walks through the XML document at step 112 and builds XML records by parsing the XML data into a more accessible form using DOM or SAX.

DOM (Document Object Model) is a known applications programming interface which parses XML documents into a tree structure of elements and attributes, so they can be analyzed and manipulated. DOM also provides access to the structure through a set of Objects which provided well-known interfaces.

Another parser which could be used to perform this step is SAX (Simple API for XML). SAX parsers only produce a series of parse events, while DOM parsers produce a complete parse tree representation of the data.

While SAX and DOM provide standard mechanisms for reading XML documents, they work at a low level. To use DOM as a manual tool, for example, would require the developer to have a detailed understanding of how to use the API to navigate nodes, elements, attributes, and to extract textual content and then convert the text to useful program data types. This process would be tedious and error prone.

Then, at step 114, the mapping data associated with the XML record is identified. This mapping data would have been generated using the algorithm of FIG. 7, and will correlate the received XML data with the desired Java output Object. As noted above, this mapping data is referred to as “metadata” for the node. The metadata drives the iterations and data populating that must be performed for the node at steps 116-130, and of course, includes the namespace data.

The metadata indicates what Java Object is required, and that Object is to be instantiated at step 126. As part of this exercise, a query is made to determine the field descriptors of the Object so they can be populated with data. A corresponding Java object is then instantiated at step 116.

As shown below with respect to Examples 1 and 4 which follow, occurrences of multiple lines of XML with the same name, will generate mapping data for distinct and separate Objects. For example, two occurrences of elements called “name” may result in the following mapping data:

-   -   1. Name of the object attribute: firstName Location of XML data:         first:NAME Namespace resolver:         first=“http://www.oracle.com/first”     -   2. Name of the object attribute: lastName Location of XML data:         last:NAME Namespace resolver: last=“http://www.oracle.com/last”         Hence, the occurrence of two elements with the same name is         easily handled during the XML to Object conversion stage. The         two elements are considered to be different nodes, and they         generate two different Objects—firstName and lastName.

The program then uses the loop 118 to walk through each mapping related to the targeted XML code, the tree performing steps 120-130 for each mapping. The loop starts at the desired entry point in the XML record which could be the root, but does not have to be. Generally, the tree would be traversed from the root node down.

For each mapping, the algorithm executes an XPath query at step 120 to collect data relative to the current XML record. XPath queries are used to specify locations in XML trees, and to collect information from those locations. As noted above, XML documents are highly structured and can be considered as trees of nodes. XPath queries are written using paths through those trees of nodes.

For example, in a XML document containing lists of CDs, such as this:

<catalog>   <cd>     <title>Christmas Songs</title>     <artist>The Rockers</artist>     <price>10.90</price>     <year>1985</year>   </cd>   <cd>     <title>Boring Songs</title>     <artist>Slim Sam</artist>     <price>9.90</price>     <year>1988</year>   </cd> . </catalog> an XPath query “catalog/cd/price” will select all of the price nodes from the XML document. Other more elaborate queries may be made using different tests (for example, identifying nodes with values greater than or less than a certain amount), or varying the paths (wildcards, for example, may be used in the paths, such as “catalog/*/price”). These variations would be known to one skilled in the art.

The XPath queries are used to collect the data needed to affect the desired mapping. Once this data has been collected, the corresponding Java Object or Objects can be populated with data per subroutine 122.

Subroutine 122 populates the Java Object(s) differently depending on whether the XML data defines structure (an object relationship) or data (a simple relationship). The nature of the XML data is determined at step 124 simply by checking the “Mapping Type” field of the metadata for the node (see Example 1 for additional details). If the metadata indicates that the XML node is “simple”, then the routine passes control to step 126 where the simple XML data is converted to be compatible with the Java Object's attribute. The simple XML data is then assigned to the attribute at step 128, and the routine is complete for this node.

If the metadata indicates that the XML node is a structural object, then the routine assigns that returned object to the Object attribute at step 130, and control returns to step 118 so that additional mappings can be considered. These additional mappings will consist of lower levels of XML data. Steps 116 through 130 are repeated for each successive lower level of XML data.

Once it has been determined at step 118 that all of the mappings have been considered, the routine passes control to step 132, where the completed instance of the Java Object is returned so it can be processed as required. In the event that the XML document is a database query, for example, the Object is then executed so that the database query can be made. If additional XML elements must be converted (i.e. there are additional nodes in the XML record), then control passes to step 120, where the next node is considered.

In short, when an XML document is being converted to Object data each of the mappings is processed for each of the Objects mapped attributes. Namespace data is included in the metadata for a given node so there are no problems with XML elements which otherwise have the same name. From the perspective of the Object data, nothing outstanding is occurring because the metadata includes separate and distinct identifiers for these nodes, even though they had the same XML name.

FIG. 9 depicts a flow diagram of a method for converting a Java class into an XML representation. This method is complementary to that of FIG. 8, and requires that the same set-up routine of FIG. 7 be performed ahead of time.

As in the case of the XML to Object conversion, this routine responds to a request to convert all or a portion of a targeted Object to XML format. To begin with, an Object is received at step 140, and the corresponding mapping data is identified at step 142. As noted above, the mapping data (or metadata) developed during the set-up routine of FIG. 7, can be used.

The routine then generates a new XML record corresponding to the mapping, at step 144, and walks through the received Object, considering one Object at a time, using the control loop through step 146. For each Object that is encountered, XML document structure is generated at step 148, according to the XPath data for the current mapping. Control then passes to subroutine 150.

The subroutine first determines whether a given node is a simple node or an object node (defining XML structure), at step 152. If the node is a simple node, then control passes to step 154 where the simple value is converted to be compatible with the XML document, and the data is subsequently added to the XML document as a text node in step 156. If the node is determined to be an object node at step 152, then the object is converted to XML at step 158, and control passes back to step 142 to iterate over lower levels of Objects.

As noted above, the metadata for a node identifies the XML name and XPath. It also includes a namespace resolver so that nodes which rely on a particular namespace can be properly handled.

Once it has been determined at step 146 that all of the mappings have been considered, control passes to step 160 where the XML record is returned and is processed as required. Generally, XML records are generated so that they can be transmitted as part of a web service, so step 160 will typically consist of transmitting the completed XML record to a remote server. Alternatively, XML records could be stored in memory, stored in a database, processed as they are generated, or handled in some other manner.

The only complication with the algorithm of FIG. 9 is in the generation of the appropriate XML structure at step 152. The metadata for a node will include the desired XPath data, as determined by the user during the set-up stage. The details of how this is done are clear from the examples which follow.

EXAMPLE 1 Mapping—Simple Values

In the example below the element “NAME” from the “http://www.oracle.com/first” namespace represents the customer's first name, and the element “NAME” from the “http://www.oracle.com/last” namespace represents the customer's last name:

<CUSTOMER xmlns:first=“http://www.oracle.com/first”   xmlns:last=“http://www.oracle.com/last”>   <first:NAME>Jane</first:NAME>   <last:NAME>Doe</last:NAME> </CUSTOMER> These namespace data will be included in the metadata for these nodes so that the information can be preserved.

Thus, mappings will be generated for these nodes including: a mapping type which determines whether the XML element is intended to contain data as opposed to defining structure (i.e. a “simple” mapping), an Object attribute, an XPath which locates the destination in the XML document and a namespace resolver:

-   -   firstName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: firstName     -   XPath: first:NAME/text( )     -   Namespace resolver: first=“http://www.oracle.com/first”     -   lastName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: lastName     -   XPath: last:NAME/text( )     -   Namespace resolver: last=“http://www.oracle.com/last”         Note that existing code conversion and mapping tools will not         recognize the namespace data of the XML elements as significant         and will not preserve it.

EXAMPLE 2 XML to Object Conversion—Simple Values

As shown above under Example 1, an XML document such as the following:

<CUSTOMER xmlns:first=“http://www.oracle.com/first”   xmlns:last=“http://www.oracle.com/last”>   <first:NAME>Jane</first:NAME>   <last:NAME>Doe</last:NAME> </CUSTOMER> will allow the following mapping data to be generated:

-   -   firstName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: firstName     -   XPath: first:NAME/text( )     -   Namespace resolver: first=“http://www.oracle.com/first”     -   lastName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: lastName     -   XPath: last:NAME/text( )     -   Namespace resolver: last=“http://www.oracle.com/last”

When an XML document is being converted to object data each of the mappings is processed for each of the objects mapped attributes. The XPath statement used to specify the location of the XML data is executed and the resulting XML data is passed to the mapping to be converted to object data, which is set on the object. It is not necessary for the prefix used in XPath that specifies the location of XML data to match the prefix used in the document since the prefix is converted to the real namespace using the namespace resolver.

Thus, the following Object code will be generated:

-   -   Customer (firstName=“Jane”, lastName=“Doe”)

This Object code preserves all of the “information” from the original XML document, when considered with the mapping data, so the original XML document can be generated.

EXAMPLE 2b XML to Object Conversion—Simple Values

It is important to node that the prefixes used in the document (in example 2 they are “first” & “last”, in example 2b they are “ns1” & “ns2”). Do not need to be the same prefixes used in the XPath specified in the mapping.

<CUSTOMER xmlns:ns1=“http://www.oracle.com/first”   xmlns:ns2=“http://www.oracle.com/last”>   <ns1:NAME>Jane</ns1:NAME>   <ns2:NAME>Doe</ns2:NAME> </CUSTOMER> The above document can be converted to objects using the same metadata that was specified in example 2 even though different prefixes were used. This is because even though the prefixes are different they represent the same namespaces:

-   -   firstName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: firstName     -   XPath: first:NAME/text( )     -   Namespace resolver: first=“http://www.oracle.com/first”     -   lastName Mapping     -   Mapping Type: direct mapping     -   Object Attribute: lastName     -   XPath: last:NAME/text( )     -   Namespace resolver: last=“http://www.oracle.com/last”

Thus, the following Object code will be generated:

-   -   Customer (firstName=“Jane”, lastName=“Doe”)

If the metadata were used to convert the objects back to XML the resulting XML document would be:

<CUSTOMER xmlns:first=“http://www.oracle.com/first”   xmlns:last=“http://www.oracle.com/last”>   <first:NAME>Jane</first:NAME>   <last:NAME>Doe</last:NAME> </CUSTOMER> Note that the prefixes specified in the XPath are used to create the resulting document instead of the original prefixes. No information is lost by renaming the prefix.

EXAMPLE 3 Object to XML Conversion—Simple Values

The complement to Example 2 is the conversion from Object format to XML. This would proceed along the following lines, the Object source:

Customer (firstName=“Jane”, lastName=“Doe”) being converted to:

<CUSTOMER xmlns:first=“http://www.oracle.com/first”   xmlns:last=“http://www.oracle.com/last”>   <first:NAME>Jane</first:NAME>   <last:NAME>Doe</last:NAME> </CUSTOMER>

When the object data is converted to XML form the prefixes used to specify the location of XML data are used to construct the document. In this case, the node metadata dictate that the firstName and lastName Objects should map onto XML elements with namespaces of xmlns:first=“http://www.oracle.com/first” and xmlns:last=“http://www.oracle.com/last” respectively. These namespaces are declared in the line of the XML document in which they are used, or at some point before that line, and are referred to by prefixes where required, as known in the art.

EXAMPLE 4 Mapping—Object Values

In the example below the element “email:ADDRESS” from the “http://www.oracle.com/email” namespace represents the customer's e-mail address, and the element “mailing:ADDRESS” from the “http://www.oracle.com/mailing” namespace represents the customer's mailing address:

<CUSTOMER xmlns:email=“http://www.oracle.com/email”   xmlns:mailing=“http://www.oracle.com/mailing”>   <email:ADDRESS>     <email:USER-ID>jane.doe</email:USER-ID>     <email:DOMAIN>oracle.com</email:DOMAIN>   </email:ADDRESS>   <mailing:ADDRESS>     <mailing:STREET>123 Any Street</mailing:STREET>     <mailing:CITY>Any Town</mailing:CITY>     <mailing:PROVINCE>Ontario</mailing:PROVINCE>     <mailing:POST-CODE>A1B2C3</mailing:POST-CODE>   </mailing:ADDRESS> </CUSTOMER> These namespace data will be included in the metadata for these nodes so that the namespace information can be preserved.

Thus, mappings will be generated for these nodes including: a mapping type which determines whether the XML element is intended to define structure (a “complex” mapping), an Object attribute, an XPath which locates the destination in the XML document and a namespace resolver. The “address mapping” element is a complex element (i.e. it defines structure rather than data), so it has a “reference descriptor” which directs the program to the “street Mapping” and “city Mapping” data:

-   -   billingAddress Mapping     -   Mapping Type: composite Object mapping     -   Object Attribute: billingAddress     -   XPath: email:ADDRESS     -   Reference Descriptor: Address     -   Namespace resolver: email=“http://www.oracle.com/email”     -   shippingAddress Mapping     -   Mapping Type: composite Object mapping     -   Object Attribute: shippingAddress     -   XPath: mailing:ADDRESS     -   Reference Descriptor: Address     -   Namespace resolver: mailing=“http://www.oracle.com/mailing”

Mapping data will also be generated for each Address attribute that will be converted to XML (i.e. the USER-ID, DOMAIN, STREET, CITY, PROVINCE AND POST-CODE). The mapping data for these simple XML elements would be along the lines of those shown under Example 1 above.

Note again, that existing code conversion and mapping tools will not recognize the namespace data from the XML elements as being significant and will not store the namespace data. Also, note that existing conversion tools do not consider whether XML elements contain data or define structure. Thus, they generate a separate object for each XML element. This results in unnecessary layers, and confusing code.

EXAMPLE 5 Object Values—XML to Object Conversion

As noted above, object elements are XML elements which include structure rather than data. The XML structure must be reconstructable, but it is not desirable that a separate Java Object be generated for each nesting element in the structure.

Thus, if the metadata described under Example 4 above is used for the following XML document:

<CUSTOMER xmlns:email=“http://www.oracle.com/email”   xmlns:mailing=“http://www.oracle.com/mailing”>   <email:ADDRESS>     <email:USER-ID>jane.doe</email:USER-ID>     <email:DOMAIN>oracle.com</email:DOMAIN>   </email:ADDRESS>   <mailing:ADDRESS>     <mailing:STREET>123 Any Street</mailing:STREET>     <mailing:CITY>Any Town</mailing:CITY>     <mailing:PROVINCE>Ontario</mailing:PROVINCE>     <mailing:POST-CODE>A1B2C3</mailing:POST-CODE>   </mailing:ADDRESS> </CUSTOMER> then the resulting Java Object code will be:

-   -   Customer (emailAddress=anEmailAddress,         mailingAddress=aMailingAddress)

EXAMPLE 6 Object Values—Object to XML Conversion

The complement to Example 5 is the conversion of Object code to an XML document. This will proceed as follows. Note that this process requires the algorithm to obtain the mapping data for the simple elements referred to by the Object elements (referred to above, as “iterating” through the tree).

Thus, given source Java code such as:

-   -   Customer (emailAddress=anEmailAddress,         mailingAddress=aMailingAddress)         and mapping data as shown above with respect to Example 4, the         routine of the invention will generate the following XML code:

<CUSTOMER xmlns:email=“http://www.oracle.com/email”  xmlns:mailing=“http://www.oracle.com/mailing”>  <email:ADDRESS>   <email:USER-ID>jane.doe</email:USER-ID>   <email:DOMAIN>oracle.com</email:DOMAIN>  </email:ADDRESS>  <mailing:ADDRESS>  <mailing:STREET>123 Any Street</mailing:STREET>   <mailing:CITY>Any Town</mailing:CITY>   <mailing:PROVINCE>Ontario</mailing:PROVINCE>   <mailing:POST-CODE>A1B2C3</mailing:POST-CODE>  </mailing:ADDRESS> </CUSTOMER> Other Options and Alternatives

The invention is not limited by the nature of the communication network or the underlying computer system to which it is applied. The invention could be applied over any computer network or computer system, using any manner of platform. Client computers may be any form of interface to the system including for example, a desktop or laptop computer, smart terminal, personal digital assistant (PDA), point of sale computer, information kiosk, Internet-ready telephone or other similar wireless or hard-wired interface known in the art.

The communications between the components in the system may be done over any communication network known in the art, and may consist of several different networks working together. These networks may include for example, wireless networks such as cellular telephone networks, the public switched telephone network, cable television networks, the Internet, ATM networks, frame relay networks, local area networks (LANs) and wide area networks (WANs). The client computers may, for example, access the system via an Internet Service Provider (ISP) using a cable modem, telephone line mode, or wireless connection. The invention is not limited by the nature of any of these communication networks.

It would be clear to one skilled in the art, how to implement these and other variations in view of the description of the invention herein.

CONCLUSIONS

While particular embodiments of the present invention have been shown and described, it is clear that changes and modifications may be made to such embodiments without departing from the true scope and spirit of the invention.

The method steps of the invention may be embodiment in sets of executable machine code stored in a variety of formats such as Object code or source code. Such code is described generically herein as programming code, or a computer program for simplification. Clearly, the executable machine code may be integrated with the code of other programs, implemented as subroutines, by external program calls or by other techniques as known in the art.

The embodiments of the invention may be executed by a computer processor or similar device programmed in the manner of method steps, or may be executed by an electronic system which is provided with means for executing these steps. Similarly, an electronic memory medium such computer diskettes, CD-Roms, Random Access Memory (RAM), Read Only Memory (ROM) or similar computer software storage media known in the art, may be programmed to execute such method steps. As well, electronic signals representing these method steps may also be transmitted via a communication network. 

1. A method for converting data in an Object model format to a markup language format, comprising the steps of: identifying an input Object, a destination markup language document, and a markup schema; determining mappings between said input Object and said schema, including identification of namespaces associated with elements of said input markup language document, wherein determining mappings comprises generating mapping metadata which defines how the data architecture of the markup language document maps to the Object model and which comprises executable components; considering each software Object in said input Object, and generating corresponding markup code with consideration for identification of namespaces associated with elements of said input markup language document; and storing said generated markup language code in said destination markup language document.
 2. The method of claim 1 wherein said step of determining mappings comprises the step of allowing a user to establish relationships between said destination Object and said markup schema using a graphic user interface.
 3. The method of claim 2, wherein said step of considering each software Object comprises the step of: for each node in said tree of nodes, reading the metadata for each said node.
 4. The method of claim 2, wherein said step of considering comprise the step of: for each node in said tree of nodes, generating an Object corresponding to each said node, populating attributes of said generated Object with the data of the elements based on the mapping metadata.
 5. The method of claim 2, wherein the markup language document comprises an eXtensible Markup Language (XML) document.
 6. The method of claim 2, wherein said step of considering comprises the step of: for each node in said tree of nodes, adding structure to said XML document based on data within said metadata, wherein the data is retrieved using a query based on a language which can be used for finding information in an XML document, navigating through the elements and attributes of the XML document, and computing values based on content of the XML document.
 7. The method of claim 2 wherein said markup language document has one or more elements containing data, said Object model has one or more Object classes, each Object class having one or more attributes, and said mapping data comprises a name of an Object attribute and a location of corresponding XML data.
 8. The method of claim 2 wherein said software Objects comprise Java Objects.
 9. The method of claim 2 wherein said step of determining mappings further comprises the step of distinguishing between data elements and organizational elements in said markup language document and said step of considering further comprises the step of generating markup code in accordance with whether mappings corresponding to each said software Object, are data or organizational, adding structure as required.
 10. The method of claim 2, wherein said step of determining mapping further comprises the step of presenting a namespace context of an XML element to said user via said GUI.
 11. The method of claim 1, wherein said step of generating metadata further includes the step of including a field for namespace data in said metadata.
 12. A system for communicating data comprising: a client computer; a remote server; and a communication network interconnecting said client computer and said remote server; said remote server being operable to receive XML documents from said client computer, via said communication network; and said client computer being operable to convert Object to XML format for transmission to said remote server by: identifying an input Object, a destination markup language document, and a markup schema; determining mappings between said input Object and said schema, including identification of namespaces associated with elements of said input markup language document, wherein determining mappings comprises generating mapping metadata which defines how the data architecture of the markup language code maps to the Object model and which comprises executable components; considering each software Object in said input Object, and generating corresponding markup code with consideration for identification of namespaces associated with elements of said input markup language document; and storing said generated markup language code in said destination markup language document. 